-
-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: retract v1.5.5 #249
fix: retract v1.5.5 #249
Conversation
Can you publish the v1.5.6 tag? |
I don't known how to only publish tag.... |
@black-06 I think publishing a new release with the new tag is fine. It could also help to explain what happened to people running into this. From the go module side publishing the git tag without a github release is the same as doing a release with the tag. |
On the commandline you checkout the branch/commit you want to tag and then run: |
yes I known if i push the git tag to github,it will create a tag without release. But what surprised me was that 1.5.5 wasn't pushed by me, it seemed like it was automatically generated, or someone else did it on the page |
Sorry i misundestood your question. |
I deleted the tag, but that tag shows that I pushed it, just like https://github.com/go-gorm/mysql/releases/tag/v1.5.3. |
Yeah that is strange and you should figure out why that happened. |
Aha, jinzhu manually pushed the tag. Okay, I publish it now. |
What did this pull request do?
#247, only delete tag v1.5.5 is not enough.
If we accept this mr, we need to publish v1.5.6 to retract v1.5.5 (& v1.5.6)
User Case Description